@dotnet/source-build-internal Could someone take a look at this failure?

Checkout of /mnt/vss/_work/_temp/installer/ at 24d02ee failed: LibGit2Sharp.NotFoundException: No valid git object identified by '24d02ee895f1f110aa1f4cd9576be8332ba076b1' exists in the repository.

@dotnet/source-build-internal Could someone take a look at this failure?

Checkout of /mnt/vss/_work/_temp/installer/ at 24d02ee failed: LibGit2Sharp.NotFoundException: No valid git object identified by '24d02ee895f1f110aa1f4cd9576be8332ba076b1' exists in the repository.

cc @premun

I cannot find the original issue but we have seen this issue about 3 or 4 times in the last half a year. Always only in AzDO builds, not reproducible locally and a re-run always helped. In the failing build here, we can see that only one of the two legs which are identical in this step is failing which hints that this is something fishy.

There is something about the way AzDO gives us the cloned installer repo and even the consecutive fetch we do doesn't fix this. I am not sure what to do about this but I tried cloning the repo step by step the same way as AzDO does it (git init + remote add + fetch) but could never repro.

FWIW, the same issue showed up in another PR: #17266

@mthalman can we make this change for this target branch too?

#17232

@mthalman can we make this change for this target branch too?

#17232

Yes, that would be good.